Direct logical block addressing flash memory mass storage architecture

ABSTRACT

A nonvolatile semiconductor mass storage system and architecture can be substituted for a rotating hard disk. The system and architecture avoid an erase cycle each time information stored in the mass storage is changed. Erase cycles are avoided by programming an altered data file into an empty mass storage block rather than over itself as a hard disk would. Periodically, the mass storage will need to be cleaned up. These advantages are achieved through the use of several flags, and a map to correlate a logical block address of a block to a physical address of that block. In particular, flags are provided for defective blocks, used blocks, and old versions of a block. An array of volatile memory is addressable according to the logical address and stores the physical address.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. appln No. 09/087,720 now U.S. Pat. No. 5,924,113, issued on Jul. 13, 1999, entitled "Direct Logical Block Addressing Flash Memory Mass Storage Architecture", which is a continuation of U.S. appln Ser. No. 08/509,706 now U.S. Pat. No. 5,845,313, issued on Dec. 1, 1998, entitled "Direct Logical Block Addressing Flash Memory Mass Storage Architecture."

FIELD OF THE INVENTION

This invention relates to the field of mass storage for computers. More particularly, this invention relates to an architecture for replacing a hard disk with a semiconductor nonvolatile memory and in particular flash memory.

BACKGROUND OF THE INVENTION

Computers conventionally use rotating magnetic media for mass storage of documents, data, programs and information. Though widely used and commonly accepted, such hard disk drives suffer from a variety of deficiencies. Because of the rotation of the disk, there is an inherent latency in extracting information from a hard disk drive.

Other problems are especially dramatic in portable computers. In particular, hard disks are unable to withstand many of the kinds of physical shock that a portable computer will likely sustain. Further, the motor for rotating the disk consumes significant amounts of power decreasing the battery life for portable computers.

Solid state memory is an ideal choice for replacing a hard disk drive for mass storage because it can resolve the problems cited above. Potential solutions have been proposed for replacing a hard disk drive with a semiconductor memory. For such a system to be truly useful, the memory must be nonvolatile and alterable. The inventors have determined that FLASH memory is preferred for such a replacement.

FLASH memory is a transistor-memory cell which is programmable through hot electron, source injection, or tunneling, and erasable through Fowler-Nordheim tunneling. The programming and erasing of such a memory cell requires current to pass through the dielectric surrounding floating gatcelectrode. Because of this, such types of memory have a finite number of erase-write cycles. Eventually, the dielectric deteriorates. Manufacturers of FLASH cell devices specify the limit for the number of erase-write cycles between 100,000 and 1,000,000.

One requirement for a semiconductor mass storage device to be successful is that its use in lieu of a rotating media hard disk mass storage device be transparent to the designer and the user of a system using such a device. In other words, the designer or user of a computer incorporating such a semiconductor mass storage device could simply remove the hard disk and replace it with a semiconductor mass storage device. All presently available commercial software should operate on a system employing such a semiconductor mass storage device without the necessity of any modification.

SunDisk proposed an architecture for a semiconductor mass storage using FLASH memory at the Silicon Valley PC Design Conference on Jul. 9, 1991. That mass storage system included read-write block sizes of 512 Bytes to conform with commercial hard disk sector sizes.

Earlier designs incorporated erase-before-write architectures. In this process, in order to update a file on the media, if the physical location on the media was previously programmed, it has to be erased before the new data can be reprogrammed.

This process would have a major deterioration on overall system throughput. When a host writes a new data file to the storage media, it provides a logical block address to the peripheral storage device associated with this data file. The storage device then translates this given logical block address to an actual physical block address on the media and performs the write operation. In magnetic hard disk drives, the new data can be written over the previous old data with no modification to the media. Therefore, once the physical block address is calculated from the given logical block address by the controller, it will simply write the data file into that location. In solid state storage, if the location associated with the calculated physical block address was previously programmed, before this block can be reprogrammed with the new data, it has to be erased. In one previous art, in erase-before-write architecture where the correlation between logical block address given by the host is one to one mapping with physical block address on the media. This method has many deficiencies. First, it introduces a delay in performance due to the erase operation before reprogramming the altered information. In solid state flash, erase is a very slow process.

Secondly, hard disk users typically store two types of information, one is rarely modified and another which is frequently changed. For example, a commercial spread sheet or word processing software program stored on a user's system are rarely, if ever, changed. However, the spread sheet data files or word processing documents are frequently changed. Thus, different sectors of a hard disk typically have dramatically different usage in terms of the number of times the information stored thereon is changed. While this disparity has no impact on a hard disk because of its insensitivity to data changes, in a FLASH memory device, this variance can cause sections of the mass storage to wear out and be unusable significantly sooner than other sections of the mass storage.

In another architecture, the inventors previously proposed a solution to store a table correlating the logical block address to the physical block address. The inventions relating to that solution are disclosed in U.S. Pat. No. 5,388,083, issued on Feb. 7, 1995. U.S. Pat. No. 5,479,638 issued on Dec. 26, 1995. Those applications are incorporated herein by reference.

The inventors' previous solution discloses two primary algorithms and an associated hardware architecture for a semiconductor mass storage device. It will be understood that "data file" in this patent document refers to any computer file including commercial software, a user program, word processing software document, spread sheet file and the like. The first algorithm in the previous solution provides means for avoiding an erase operation when writing a modified data file back onto the mass storage device. Instead, no erase is performed and the modified data file is written onto an empty portion of the, mass storage.

The semiconductor mass storage architecture has blocks sized to conform with commercial hard disk sector sizes. The blocks are individually erasable. In one embodiment, the semiconductor mass storage can be substituted for a rotating hard disk with no impact to the user, so that such a substitution will be transparent. Means are provided for avoiding the erase-before-write cycle each time information stored in the mass storage is changed.

According to the first algorithm, erase cycles are avoided by programming an altered data file into an empty block. This would ordinarily not be possible when using conventional mass storage because the central processor and commercial software available in conventional computer systems are not configured to track continually changing physical locations of data files. The previous solution includes a programmable map to maintain a correlation between the logical address and the physical address of the updated information files.

All the flags, and the table correlating the logical block address to the physical block address are maintained within an array of CAM cells. The use of the CAM cells provides very rapid determination of the physical address desired within the mass storage, generally within one or two clock cycles. Unfortunately, as is well known, CAM cells require multiple transistors, typically six. Accordingly, an integrated circuit built for a particular size memory using CAM storage for the tables and flags will need to be significantly larger than a circuit using other means for just storing the memory.

The inventors proposed another solution to this problem which is disclosed in U.S. Pat. No. 5,485,595, issued on Jan. 16, 1996. That application is incorporated herein by reference.

This additional previous solution invented by these same inventors is also for a nonvolatile memory storage device. The device is also configured to avoid having to perform an erase-before-write each time a data file is changed by keeping a correlation between logical block address and physical block address in a volatile space management RAM. Further, this invention avoids the overhead associated with CAM cell approaches which require additional circuitry.

Like the solutions disclosed above by these same inventors, the device includes circuitry for performing the two primary algorithms and an associated hardware architecture for a semiconductor mass storage device. In addition, the CAM cell is avoided in this previous solution by using RAM cells.

Reading is performed in this previous solutions by providing the logical block address to the memory storage. The system sequentially compares the stored logical block addresses until it finds a match. That data file is then coupled to the digital system. Accordingly, the performance offered by this solution suffers because potentially all of the memory locations must be searched and compared to the desired logical block address before the physical location of the desired information can be determined.

What is needed is a semiconductor hard disk architecture which provides rapid access to stored data without the excessive overhead of CAM cell storage.

SUMMARY OF THE INVENTION

The present invention is for a nonvolatile memory storage device. The device is configured to avoid having to perform an erase-before-write each time a data file is changed. Further, to avoid the overhead associated with CAM cells, this approach utilizes a RAM array. The host system maintains organization of the mass storage data by using a logical block address. The RAM array is arranged to be addressable by the same address as the logical block addresses of the host. Each such addressable location in the RAM includes a field which holds the physical address of the data in the nonvolatile mass storage expected by the host. This physical block address information must be shadowed in the nonvolatile memory to ensure that the device will still function after resuming operation after a power down because Rams are volatile memory devices. In addition, status flags are also stored for each physical location. The status flags can be stored in either the nonvolatile media or in both the RAM and in the nonvolatile media.

The device includes circuitry for performing two primary algorithms and an associated hardware architecture for a semiconductor mass storage device. The first algorithm provides a means for mapping of host logical block address to physical block address with much improved performance and minimal hardware assists. In addition, the second algorithm provides means for avoiding an erase-before-write cycle when writing a modified data file back onto the mass storage device. Instead, no erase is performed and the modified data file is written onto an empty portion of the mass storage.

Reading is performed in the present invention by providing the logical block address to the memory storage. The RAM array is arranged so that the logical block address selects one RAM location. That location contains the physical block address of the data requested by the host or other external system. That data file is then read out to the host.

According to the second algorithm, erase cycles are avoided by programming an altered data file into an empty mass storage block rather than itself after an erase cycle of the block as done on previous arts.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a schematic block diagram of an architecture for a semiconductor mass storage according to the present invention.

FIG. 2 shows an alternative embodiment to the physical block address 102 of the RAM storage of FIG. 1.

FIG. 3 shows a block diagram of a system incorporating the mass storage device of the present invention.

FIGS. 4 through 8 show the status of several of the flags and information for achieving the advantages of the present invention.

FIG. 9 shows a flow chart block diagram of the first algorithm according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

FIG. 1 shows an architecture for implementation of a solid state storage media according to the present invention. The storage media is for use with a host or other external digital system. The mass storage is partitioned into two portions, a volatile RAM array 100 and a nonvolatile array 104. According to the preferred embodiment, all of the nonvolatile memory storage is FLASH. The FLASH may be replaced by EEPROM. The RAM can be of any convenient type.

The memory storage 104 is arranged into N blocks of data from zero through N-1. Each of the blocks of data is M Bytes long. In the preferred embodiment, each data block is 512 Bytes long to correspond with a sector length in a commercially available hard disk drive plus the extra numbers of bytes to store the flags and logical block address information and the associated ECC. The memory 104 can contain as much memory storage as a user desires. An example of a mass storage device might include 100 M Byte of addressable storage.

There are a plurality of RAM locations 102. Each RAM location 102 is uniquely addressable by controller using an appropriate one of the logical block addresses provided by the host system or the actual physical address of the nonvolatile media. The RAM location 102 contains the physical block address of the data associated with the logical block address and the flags associated with a physical block address on the nonvolatile media.

It is possible that the physical block address can be split into two fields as shown in FIG. 2. These fields can be used for cluster addresses of a group of data blocks. The first such field 290 is used to select a cluster address and the second such field 292 can be used to select the start address of the logical block address associated with this cluster.

A collection of information flags is also stored for each nonvolatile memory location 106. These flags include an old/new flag 100, a used/free flag 112, a defect flag 114, and a single/sector flag 116. Additionally, there is also a data store 122.

When writing data to the mass storage device of the present invention, a controller determines the first available physical block for storing the data. The RAM location 102 corresponding to the logical block address selected by the host is written with the physical block address where the data is actually stored within the nonvolatile memory array in 104 (FIG. 1).

Assume for example that a user is preparing a word processing document and instructs the computer to save the document. The document will be stored in the mass storage system. The host system will assign it a logical block address. The mass storage system of the present invention will select a physical address of an unused block orblocks in the mass storage for storing the document. The address of the physical block address will be stored into the RAM location 102 corresponding to the logical block address. As the data is programmed, the system of the present invention also sets the used/free flag 112 in 104 and 293 to indicate that this block location is used. One used/free flag 112 is provided for each entry of the nonvolatile array 104.

Later, assume the user retrieves the document, makes a change and again instructs the computer to store the document. To avoid an erase-before-write cycle, the system of the present invention provides means for locating a block having its used/free flag 112 in 100 unset (not programmed) which indicates that the associated block is erased. The system then sets the used/free flag for the new block 112 of 106 and 293 of 100 and then stores the modified document in that new physical block location 106 in the nonvolatile array 104. The address of the new physical block location is also stored into the RAM location 102 corresponding the logical block address, thereby writing over the previous physical block location in 102. Next, the system sets the old/new flag 110 of the previous version of the document indicating that this is an old unneeded version of the document in 110 of 104 and 293 of 100. In this way, the system of the present invention avoids the overhead of an erase cycle which is required in the erase-before-write of conventional systems to store a modified version of a previous document.

Because of RAM array 100 will lose its memory upon a power down condition, the logical block address with the active physical block address in the media is also stored as a shadow memory 108 in the nonvolatile array 104. It will be understood the shadow information will be stored into the appropriate RAM locations 102 by the controller. During power up sequence, the RAM locations in 100 are appropriately updated from every physical locations in 104, by reading the information 106 of 104. The logical address 108 of 106 is used to address the RAM location of 100 to update the actual physical block address associated with the given logical block address. Also since 106 is the actual physical block address associated with the new data 122, the flags 110, 112, 114, and 116 are updated in 293 of 102 with the physical block address of 106 in 100. It will be apparent to one of ordinary skill in the art that the flags can be stored in either the appropriate nonvolatile memory location 106 or in both the nonvolatile memory location and also in the RAM location 102 associated with the physical block address.

During power up, in order to assign the most recent physical block address assigned to a logical block address in the volatile memory 100, the controller will first reads the Flags 110,112,114, and 116 portion of the nonvolatile memory 104 and updates the flags portion 293 in the volatile memory 100. Then it reads the logical block address 108 of every physical block address of the nonvolatile media 104 and by tracking the flags of the given physical block address in the volatile memory 100, and the read logical block address of the physical block address in the nonvolatile memory 104, it can update the most recent physical block address assigned to the read logical block address in the volatile memory 100.

FIG. 3 shows a block diagram of a system incorporating the mass storage device of the present invention. An external digital system 300 such as a host computer, personal computer and the like is coupled to the mass storage device 302 of the present invention. A logical block address is coupled via an address bus 306 to the volatile RAM array 100 and to a controller circuit 304. Control signals are also coupled to the controller 304 via a control bus 308. The volatile RAM array 100 is couple via data paths 140 for providing the physical block address to the nonvolatile RAM array 104. The controller 304 is coupled to control both the volatile RAM 100, the nonvolatile array 104, and for the generation of all flags.

A simplified example, showing the operation of the write operation according to the present invention is shown in FIGS. 4 through 8. Not all the information flags are shown to avoid obscuring these features of the invention in excessive detail. The data entries are shown using decimal numbers to further simplify the understanding of the invention. It will be apparent to one of ordinary skill in the art that in a preferred embodiment binary counting will be used.

FIG. 4 shows an eleven entry mass storage device according to the present invention. There is no valid nor usable data stored in the mass storage device of FIG. 4. Accordingly, all the physical block addresses are empty. The data stored in the nonvolatile mass storage location `6` is filled and old. Additionally, location `9` is defective and cannot be used.

The host directs the mass storage device of the example to write data pursuant to the logical block address `3` and then to `4`. The mass storage device will first write the data associated with the logical block address `3`. The device determines which is the first unused location in the nonvolatile memory. In this example, the first empty location is location `0`. Accordingly, FIG. 5 shows that for the logical block address `3`, the corresponding physical block address `0` is stored and the used flag is set in physical block address `0`. The next empty location is location `1`. FIG. 6 shows that for the logical block address `4`, the corresponding physical block address `1` is stored and the used flag is set in physical block address `1`.

The host instructs that something is to be written to logical block address `3` again. The next empty location is determined to be location `2`. FIG. 7 shows that the old flag in location `0` is set to indicate that this data is no longer usable, the used flag is set in location `2` and the physical block address in location `3` is changed to `2`.

Next, the host instructs that something is to be written to logical block address `4` again. The next empty location is determined to be location `3`. FIG. 8 shows that the old flag in location `1` is set to indicate that this data is no longer usable, the used flag is set in location `3` and the physical block address in location `4` is changed to `3`. (Recall that there is generally no relation between the physical block address and the data stored in the same location.)

FIG. 9 shows algorithm 1 according to the present invention. When the system of the present invention receives an instruction to program data into the mass storage (step 200), then the system attempts to locate a free block (step 202), i.e., a block having an-unset (not programmed) used/free flag. If successful, the system sets the used/free flag for that block and programs the data into that block (step 206).

If on the other hand, the system is unable to locate a block having an unset used/free flag, the system erases the flags (used/free and old/new) and data for all blocks having a set old/new flag and unset defect flag (step 204) and then searches for a block having an unset used/free flag (step 202). Such a block has just been formed by step 204. The system then sets the used/flag for that block and programs the data file into that block (step 206).

If the data is a modified version of a previously existing file, the system must prevent the superseded version from being accessed. The system determines whether the data file supersedes a previous data file (step 208). If so, the system sets the old/new flag associated with the superseded block (step 210). If on the other hand, the data file to be stored is a newly created data file, the step of setting the old/new flag (step 210) is skipped because there is no superseded block. Lastly, the map for correlating the logical address 108 to the physical address 130 is updated (step 212).

By following the procedure outlined above, the overhead associated with an erases cycle is avoided for each write to the memory 104 except for periodically. This vastly improves the performance of the overall computer system employing the architecture of the present invention.

In the preferred embodiment of the present invention, the programming of the flash memory follows the procedure commonly understood by those of ordinary skill in the art. In other words, the program impulses are appropriately applied to the bits to be programmed and then compared to the data being programmed to ensure that proper programming has occurred. In the event that a bit fails to be erased or programmed properly, a defect flag 114 (in FIG. 1) is set which prevent that block from being used again.

The present invention is described relative to a preferred embodiment. Modifications or improvements which apparent to one of ordinary skill in the art after reading this disclosure are deemed within the spirit and scope of this invention. 

What we claim is:
 1. A nonvolatile storage system having nonvolatile memory, the storage system being coupled to an external digital system for storing binary information therefor in the nonvolatile memory, the external digital system including means for generating a plurality of logical block addresses for use in storing or reading data, the storage system comprising:a. a volatile memory device having a plurality of volatile memory locations each of which is uniquely addressable by one of the logical block addresses, and wherein each of the volatile memory locations is configured to store a physical block address without requiring the storage of a corresponding logical block address; b. one or more nonvolatile memory devices having a plurality of nonvolatile data blocks, each block being selectively programmable and erasable, being uniquely addressable by one of the physical block addresses, and having associated therewith at least one flag stored indicative of the status of the block; and c. a controller for receiving a block of data from the external digital system to be stored in the one or more nonvolatile memory devices, for receiving a target logical block address from the external system, for identifying a free block within the nonvolatile data blocks having no data stored therein, for storing the physical block address of the free block in the volatile memory location that corresponds to the target logical block address, and for periodically erasing all blocks of the nonvolatile memory devices having flags which are set, whereby an erase cycle is not needed each time the external system writes to the storage device, wherein the at least one flag associated with the block is copied from the nonvolatile memory devices to the volatile memory locations.
 2. A nonvolatile storage system as recited in claim 1 wherein the target logical block address is stored in the corresponding block of the one or more nonvolatile memory devices.
 3. A nonvolatile storage system as recited in claim 1 wherein the volatile memory device is comprised of a random access memory (RAM) type of memory.
 4. A nonvolatile storage system as recited in claim 1 wherein the one or more nonvolatile memory devices are comprised of FLASH cells.
 5. A nonvolatile storage system as recited in claim 1 wherein the volatile memory device is located externally to the controller.
 6. A nonvolatile storage system as recited in claim 1 wherein the volatile memory device is resident within the controller.
 7. A nonvolatile storage system as recited in claim 1 wherein the controller includes means for addressing one of the plurality of volatile memory locations using a desired logical block address, means for retrieving a physical block address stored in the volatile memory location that corresponds to the desired logical block address, means for reading a block within the one or more nonvolatile memory devices identified by the retrieved physical block address and means for coupling the block read from the one or more nonvolatile memory devices to the external system.
 8. A nonvolatile storage system as recited in claim 1 wherein the at least one flag includes a used/free flag for indicating whether or not a block contains data.
 9. A nonvolatile storage system as recited in claim 8 wherein the used/free flag is stored in the volatile memory locations.
 10. A nonvolatile storage system as recited in claim 9 wherein the controller for further storing the logical block addresses in corresponding blocks of the one or more nonvolatile memory devices and during power-up utilizing the stored logical addresses for copying the used/free flags to the volatile memory locations.
 11. A nonvolatile storage system as recited in claim 1 wherein each of the plurality of volatile memory locations being further uniquely addressable by one of the physical block addresses, the controller, upon power-up, being operative to address the volatile memory locations using the physical block addresses for updating the used/free flags of the volatile memory locations with the corresponding used/free flags of the one or more nonvolatile memory devices.
 12. A nonvolatile storage system as recited in claim 11 wherein the logical block addresses are stored in corresponding blocks of the one or more nonvolatile memory devices and upon power-up, the controller being operative to read the logical block addresses stored in the nonvolatile memory device, address the volatile memory locations by the read logical block addresses, and based upon the updated used/free flags, update the physical block addresses in the volatile memory locations that were most recently assigned to the logical block addresses prior to power-up.
 13. A nonvolatile storage system as recited in claim 1 wherein the at least one flag associated with the block is copies from the nonvolatile memory devices to the volatile memory locations during power-up.
 14. A nonvolatile storage system as recited in claim 1 wherein the at least one flag includes old/new flags for indicating, when set, that the block contains data that has been superseded.
 15. A nonvolatile storage system as recited in claim 14 wherein the controller includes means for periodically erasing blocks that have set old/new flags.
 16. A nonvolatile storage system as recited in claim 14 wherein the old/new flag is stored in the volatile memory locations.
 17. A nonvolatile storage system as recited in claim 16 wherein the controller further stores the logical block addresses in corresponding blocks of the one or more nonvolatile memory devices and during power-up utilizing the stored logical addresses for copying the old/new flags to the volatile memory locations.
 18. A nonvolatile storage system as recited in claim 16 wherein each of the plurality of volatile memory locations being further uniquely addressable by one of the physical block addresses, the controller, upon power-up, being operative to address the volatile memory locations using the physical block addresses for updating the old/new flag of the volatile memory locations with the corresponding old/new flags of the one or more nonvolatile memory devices.
 19. A nonvolatile storage system as recited in claim 16 wherein the logical block addresses are stored in corresponding blocks of the one or more nonvolatile memory devices and upon power-up, the controller being operative to read the logical block addresses stored in the nonvolatile memory devices, address the volatile memory locations by the logical block addresses, and based upon the updated old/new flags, update the physical block addresses in the volatile memory locations that were most recently assigned to the logical block addresses prior to power-up.
 20. A nonvolatile storage system as recited in claim 1 wherein the at least one flag includes a defect flag for indicating whether or not the block is defective.
 21. A nonvolatile storage system as recited in claim 20 wherein the defect flag is stored in the volatile memory locations.
 22. A nonvolatile storage system as recited in claim 21 wherein the controller further stores the logical block addresses in corresponding blocks of the one or more nonvolatile memory devices and during power-up utilizing the stored logical addresses for copying the defect flags to the volatile memory locations.
 23. A nonvolatile storage system as recited in claim 21 wherein each of the plurality of volatile memory locations being further uniquely addressable by one of the physical block addresses, the controller, upon power-up, being operative to address the volatile memory locations using the physical block addresses for updating the defect flag of the volatile memory locations with the corresponding old/new flags of the one or more nonvolatile memory devices.
 24. A nonvolatile storage system as recited in claim 21 wherein the logical block addresses are stored in corresponding blocks of the one or more nonvolatile memory devices and upon power-up, the controller being operative to read the logical block addresses stored in the nonvolatile memory devices, address the volatile memory locations by the logical block addresses, and based upon the updated defect flags, update the physical block addresses in the volatile memory locations that were most recently assigned to the logical block addresses prior to power-up.
 25. A nonvolatile memory system having a nonvolatile memory, the storage system being coupled to an external digital system for storing binary information therefore in the nonvolatile memory, the storage system for receiving, from the external digital system, a plurality of logical block addresses for identifying the binary information and generating a plurality of physical block addresses corresponding to the logical block addresses, each physical block address for use in identifying locations within the nonvolatile memory for storing or reading the binary information, comprising:a. a volatile memory device having a plurality of volatile memory locations each of which is uniquely addressable by one of the logical block addresses and one of the physical block addresses, the volatile memory device configured to store physical block addresses in volatile memory locations identified by the logical block addresses and further being configured to store flags in volatile memory locations identified by the physical block addresses; b. one or more nonvolatile memory devices each having a plurality of nonvolatile data blocks, each block being selectively programmable and erasable, being uniquely addressable by one of the physical block addresses, and having associated therewith shadow flags for indicating the status of the block, the one or more nonvolatile memory devices further having storage locations for storing logical block addresses in corresponding blocks of the one or more nonvolatile memory devices; and c. a controller operative to receive a block of data, identified by a target logical block address, from the external digital system for storage thereof in the one or more nonvolatile memory devices, to identify a free block within the nonvolatile data blocks having no data stored therein and having a particular physical block address, to store the received block of data and the target logical block address in the free block, to update the shadow flags so as to reflect the current status of the block identified by the target logical block address, and to store the particular physical block address and the shadow flags in the volatile memory location identified by the target logical block address, wherein during power-up the physical block addresses are used to address the volatile memory locations and update the flags thereof with the shadow flags of the nonvolatile data blocks and the logical block addresses that are stored in the nonvolatile data blocks are utilized to update the physical block addresses of the volatile memory locations with the physical block addresses that were most recently assigned to the logical block addresses prior to power-up and further wherein periodically all blocks of the one or more nonvolatile memory devices having shadow flags which are set are erased thereby avoiding the need for an erase cycle each time the external system writes to the storage device.
 26. A nonvolatile memory system as recited in claim 25 wherein the volatile memory device is comprised of random access memory (RAM) type of memory.
 27. A nonvolatile memory system as recited in claim 25 wherein the one or more nonvolatile memory devices arc comprised of FLASH cells.
 28. A nonvolatile memory system as recited in claim 25 wherein the volatile memory device is located within the controller.
 29. A nonvolatile memory system as recited in claim 25 wherein the volatile memory device is located externally to the controller.
 30. A nonvolatile memory system as recited in claim 25 wherein the shadow flags of each block include a used/free flag for indicating whether or not the corresponding block contains data.
 31. A nonvolatile memory system as recited in claim 25 wherein the shadow flags of each block include a defective flag for indicating whether or not the corresponding block is defective.
 32. A nonvolatile memory system as recited in claim 25 wherein the shadow flags of each block further include a old/new flag for indicating, when set, that the corresponding block contains data that has been superseded.
 33. A nonvolatile memory system as recited in claim 32 wherein the controller includes means for periodically erasing blocks within the nonvolatile memory devices that have set old/new flags. 